Sourced from com.google.dagger:hilt-android's releases.

Dagger 2.59

Breaking changes:

• The main change in this release is to add support for AGP 9, which requires making AGP 9 a requirement along with AGP 9’s own requirements like Gradle 9.1 (https://developer.android.com/build/releases/agp-9-0-0-release-notes).

Bug fixes/features:

• Fixed #4944, #4979: Support AGP 9 in HiltGradlePlugin (6afd7ea5a0fb84a38f2d23c990ddbd95e728a39d)

Dagger 2.58

Note: AGP 9 support was held back from this release (google/dagger#5061) because it forces users onto AGP 9. It will be available in the next Dagger release (e92e3f392).

Potential breaking changes:

• Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
• The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

• Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
• Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
• Fixes #4982:
  • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
  • Added error for binding elements names that are Java keywords. (38071c5ae)
  • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

• bd412c6 2.59 release
• 507a226 Fix upload_to_sonatype script.
• 6afd7ea Reenable AGP 9 in HiltGradlePlugin.
• 6eb10d1 Bump minimum emulator to API Level 23.
• beb47ae Update Dagger yml and README with new latest version number.
• dba58d2 Upgrade Bazel version to 8.5.0
• a54bac9 Add a test to check on framework requests on delegate chains.
• be5dbc9 Internal change
• 925e514 Internal changes
• ad02c11 Internal Changes
• Additional commits viewable in compare view

Sourced from com.google.dagger:hilt-android-compiler's releases.

Dagger 2.59

Breaking changes:

• The main change in this release is to add support for AGP 9, which requires making AGP 9 a requirement along with AGP 9’s own requirements like Gradle 9.1 (https://developer.android.com/build/releases/agp-9-0-0-release-notes).

Bug fixes/features:

• Fixed #4944, #4979: Support AGP 9 in HiltGradlePlugin (6afd7ea5a0fb84a38f2d23c990ddbd95e728a39d)

Dagger 2.58

Note: AGP 9 support was held back from this release (google/dagger#5061) because it forces users onto AGP 9. It will be available in the next Dagger release (e92e3f392).

Potential breaking changes:

• Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
• The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

• Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
• Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
• Fixes #4982:
  • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
  • Added error for binding elements names that are Java keywords. (38071c5ae)
  • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

• bd412c6 2.59 release
• 507a226 Fix upload_to_sonatype script.
• 6afd7ea Reenable AGP 9 in HiltGradlePlugin.
• 6eb10d1 Bump minimum emulator to API Level 23.
• beb47ae Update Dagger yml and README with new latest version number.
• dba58d2 Upgrade Bazel version to 8.5.0
• a54bac9 Add a test to check on framework requests on delegate chains.
• be5dbc9 Internal change
• 925e514 Internal changes
• ad02c11 Internal Changes
• Additional commits viewable in compare view

Sourced from com.google.dagger:hilt-android-testing's releases.

Dagger 2.59

Breaking changes:

• The main change in this release is to add support for AGP 9, which requires making AGP 9 a requirement along with AGP 9’s own requirements like Gradle 9.1 (https://developer.android.com/build/releases/agp-9-0-0-release-notes).

Bug fixes/features:

• Fixed #4944, #4979: Support AGP 9 in HiltGradlePlugin (6afd7ea5a0fb84a38f2d23c990ddbd95e728a39d)

Dagger 2.58

Note: AGP 9 support was held back from this release (google/dagger#5061) because it forces users onto AGP 9. It will be available in the next Dagger release (e92e3f392).

Potential breaking changes:

• Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
• The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

• Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
• Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
• Fixes #4982:
  • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
  • Added error for binding elements names that are Java keywords. (38071c5ae)
  • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

• bd412c6 2.59 release
• 507a226 Fix upload_to_sonatype script.
• 6afd7ea Reenable AGP 9 in HiltGradlePlugin.
• 6eb10d1 Bump minimum emulator to API Level 23.
• beb47ae Update Dagger yml and README with new latest version number.
• dba58d2 Upgrade Bazel version to 8.5.0
• a54bac9 Add a test to check on framework requests on delegate chains.
• be5dbc9 Internal change
• 925e514 Internal changes
• ad02c11 Internal Changes
• Additional commits viewable in compare view

Sourced from com.google.dagger.hilt.android's releases.

Dagger 2.59

Breaking changes:

• The main change in this release is to add support for AGP 9, which requires making AGP 9 a requirement along with AGP 9’s own requirements like Gradle 9.1 (https://developer.android.com/build/releases/agp-9-0-0-release-notes).

Bug fixes/features:

• Fixed #4944, #4979: Support AGP 9 in HiltGradlePlugin (6afd7ea5a0fb84a38f2d23c990ddbd95e728a39d)

Dagger 2.58

Note: AGP 9 support was held back from this release (google/dagger#5061) because it forces users onto AGP 9. It will be available in the next Dagger release (e92e3f392).

Potential breaking changes:

• Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
• The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

• Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
• Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
• Fixes #4982:
  • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
  • Added error for binding elements names that are Java keywords. (38071c5ae)
  • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

• bd412c6 2.59 release
• 507a226 Fix upload_to_sonatype script.
• 6afd7ea Reenable AGP 9 in HiltGradlePlugin.
• 6eb10d1 Bump minimum emulator to API Level 23.
• beb47ae Update Dagger yml and README with new latest version number.
• dba58d2 Upgrade Bazel version to 8.5.0
• a54bac9 Add a test to check on framework requests on delegate chains.
• be5dbc9 Internal change
• 925e514 Internal changes
• ad02c11 Internal Changes
• Additional commits viewable in compare view

Sourced from com.google.dagger:hilt-android-compiler's releases.

Dagger 2.59

Breaking changes:

• The main change in this release is to add support for AGP 9, which requires making AGP 9 a requirement along with AGP 9’s own requirements like Gradle 9.1 (https://developer.android.com/build/releases/agp-9-0-0-release-notes).

Bug fixes/features:

• Fixed #4944, #4979: Support AGP 9 in HiltGradlePlugin (6afd7ea5a0fb84a38f2d23c990ddbd95e728a39d)

Dagger 2.58

Note: AGP 9 support was held back from this release (google/dagger#5061) because it forces users onto AGP 9. It will be available in the next Dagger release (e92e3f392).

Potential breaking changes:

• Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
• The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

• Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
• Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
• Fixes #4982:
  • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
  • Added error for binding elements names that are Java keywords. (38071c5ae)
  • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

• bd412c6 2.59 release
• 507a226 Fix upload_to_sonatype script.
• 6afd7ea Reenable AGP 9 in HiltGradlePlugin.
• 6eb10d1 Bump minimum emulator to API Level 23.
• beb47ae Update Dagger yml and README with new latest version number.
• dba58d2 Upgrade Bazel version to 8.5.0
• a54bac9 Add a test to check on framework requests on delegate chains.
• be5dbc9 Internal change
• 925e514 Internal changes
• ad02c11 Internal Changes
• Additional commits viewable in compare view

Sourced from com.google.dagger:hilt-android-testing's releases.

Dagger 2.59

Breaking changes:

• The main change in this release is to add support for AGP 9, which requires making AGP 9 a requirement along with AGP 9’s own requirements like Gradle 9.1 (https://developer.android.com/build/releases/agp-9-0-0-release-notes).

Bug fixes/features:

• Fixed #4944, #4979: Support AGP 9 in HiltGradlePlugin (6afd7ea5a0fb84a38f2d23c990ddbd95e728a39d)

Dagger 2.58

Note: AGP 9 support was held back from this release (google/dagger#5061) because it forces users onto AGP 9. It will be available in the next Dagger release (e92e3f392).

Potential breaking changes:

• Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
• The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

• Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
• Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
• Fixes #4982:
  • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
  • Added error for binding elements names that are Java keywords. (38071c5ae)
  • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

• bd412c6 2.59 release
• 507a226 Fix upload_to_sonatype script.
• 6afd7ea Reenable AGP 9 in HiltGradlePlugin.
• 6eb10d1 Bump minimum emulator to API Level 23.
• beb47ae Update Dagger yml and README with new latest version number.
• dba58d2 Upgrade Bazel version to 8.5.0
• a54bac9 Add a test to check on framework requests on delegate chains.
• be5dbc9 Internal change
• 925e514 Internal changes
• ad02c11 Internal Changes
• Additional commits viewable in compare view

• bf25bb9 Release 3.4.0 (#5325)
• 1178f8a Update "Report a problem" links (#5322)
• f99d0af KTOR-9258 Add headers member function to DefaultRequestBuilder to prevent sil...
• 7452420 Yaml config. Resolve references only once. (#5320)
• 3798824 WebSockets. Added frame queues backpressure configuration. (#5274)
• 761eeac KTOR-9235: Ignore exceptions when parsing cookie expires date (#5288)
• b8817e5 KTOR-9210 Migrate Zstd into standalone module (#5318)
• f5e2864 Merge pull request #5316 from ktorio/zibet27/fix-auth-binary-compatibility
• cbcdc39 Auth. Fix binary compatibility.
• 95a7734 Fix RETURN_IN_FUNCTION_WITH_EXPRESSION_BODY_AND_IMPLICIT_TYPE
• Additional commits viewable in compare view

• bf25bb9 Release 3.4.0 (#5325)
• 1178f8a Update "Report a problem" links (#5322)
• f99d0af KTOR-9258 Add headers member function to DefaultRequestBuilder to prevent sil...
• 7452420 Yaml config. Resolve references only once. (#5320)
• 3798824 WebSockets. Added frame queues backpressure configuration. (#5274)
• 761eeac KTOR-9235: Ignore exceptions when parsing cookie expires date (#5288)
• b8817e5 KTOR-9210 Migrate Zstd into standalone module (#5318)
• f5e2864 Merge pull request #5316 from ktorio/zibet27/fix-auth-binary-compatibility
• cbcdc39 Auth. Fix binary compatibility.
• 95a7734 Fix RETURN_IN_FUNCTION_WITH_EXPRESSION_BODY_AND_IMPLICIT_TYPE
• Additional commits viewable in compare view

• bf25bb9 Release 3.4.0 (#5325)
• 1178f8a Update "Report a problem" links (#5322)
• f99d0af KTOR-9258 Add headers member function to DefaultRequestBuilder to prevent sil...
• 7452420 Yaml config. Resolve references only once. (#5320)
• 3798824 WebSockets. Added frame queues backpressure configuration. (#5274)
• 761eeac KTOR-9235: Ignore exceptions when parsing cookie expires date (#5288)
• b8817e5 KTOR-9210 Migrate Zstd into standalone module (#5318)
• f5e2864 Merge pull request #5316 from ktorio/zibet27/fix-auth-binary-compatibility
• cbcdc39 Auth. Fix binary compatibility.
• 95a7734 Fix RETURN_IN_FUNCTION_WITH_EXPRESSION_BODY_AND_IMPLICIT_TYPE
• Additional commits viewable in compare view

• bf25bb9 Release 3.4.0 (#5325)
• 1178f8a Update "Report a problem" links (#5322)
• f99d0af KTOR-9258 Add headers member function to DefaultRequestBuilder to prevent sil...
• 7452420 Yaml config. Resolve references only once. (#5320)
• 3798824 WebSockets. Added frame queues backpressure configuration. (#5274)
• 761eeac KTOR-9235: Ignore exceptions when parsing cookie expires date (#5288)
• b8817e5 KTOR-9210 Migrate Zstd into standalone module (#5318)
• f5e2864 Merge pull request #5316 from ktorio/zibet27/fix-auth-binary-compatibility
• cbcdc39 Auth. Fix binary compatibility.
• 95a7734 Fix RETURN_IN_FUNCTION_WITH_EXPRESSION_BODY_AND_IMPLICIT_TYPE
• Additional commits viewable in compare view

• bf25bb9 Release 3.4.0 (#5325)
• 1178f8a Update "Report a problem" links (#5322)
• f99d0af KTOR-9258 Add headers member function to DefaultRequestBuilder to prevent sil...
• 7452420 Yaml config. Resolve references only once. (#5320)
• 3798824 WebSockets. Added frame queues backpressure configuration. (#5274)
• 761eeac KTOR-9235: Ignore exceptions when parsing cookie expires date (#5288)
• b8817e5 KTOR-9210 Migrate Zstd into standalone module (#5318)
• f5e2864 Merge pull request #5316 from ktorio/zibet27/fix-auth-binary-compatibility
• cbcdc39 Auth. Fix binary compatibility.
• 95a7734 Fix RETURN_IN_FUNCTION_WITH_EXPRESSION_BODY_AND_IMPLICIT_TYPE
• Additional commits viewable in compare view

Sourced from org.jetbrains.kotlinx:kotlinx-serialization-core's releases.

1.10.0

This release is based on Kotlin 2.3.0 and contains all of the changes from 1.10.0-RC. The only additional change is a fix for ProtoBuf packing of Kotlin unsigned types (#3079). Big thanks to KosmX for contributing the fix.

For your convenience, the changelog for 1.10.0-RC is duplicated below:

Stabilization of APIs

kotlinx-serialization 1.10 and subsequent releases will be focused on stabilization of existing APIs. The following APIs and configuration options are no longer experimental because they're widely used without any known major issues:

• Json configuration options: decodeEnumsCaseInsensitive, allowTrailingComma, allowComments, and prettyPrintIndent. (#3100)
• @EncodeDefault annotation and its modes. (#3106)
• JsonUnquotedLiteral constructor function (#2900)
• JsonPrimitive constructor function overloads that accept unsigned types. (#3117)
• JSON DSL functions on JsonElement with Nothing? overloads. (#3117)

Readiness for return value checker

Kotlin 2.3.0 introduces a new feature aimed at helping you to catch bugs related to the accidentally ignored return value of the function. kotlinx-serialization 1.10.0-RC code is fully marked for this feature, meaning that you can get warnings for unused function calls like Json.encodeToString(...). To get the warnings, the feature has to be enabled in your project as described here.

Polymorphism improvements

Polymorphic serialization received a couple of improvements in this release:

New subclassesOfSealed utility to automatically register sealed subclasses serializers in polymorphic modules (#2201).

Use it in your SerializersModule when configuring a polymorphic hierarchy which contains both abstract and sealed classes. For example, when root of your hierarchy is an interface, but most of your inheritors are sealed classes. The new function will register all known sealed subclasses for you, so you don’t need to list them one by one. This makes writing your SerializerModules much faster and simpler. Big thanks to Paul de Vrieze for contributing this feature.

Class discriminator conflict check rework (#3105).

If a payload already contains a property with the same name as the configured discriminator (for example, type), it is called a class discriminator conflict. To produce a correct output and allow more inputs to be deserialized at the same time, the following changes were made:

• Conflicts introduced by JsonNamingStrategy transformations are now detected during serialization as well and will cause SerializationException. It also affects non-polymorphic classes.
• Conflicts from ClassDisciminatorMode.ALL_JSON_OBJECTS and SerializersModuleBuilder.polymorphicDefaultSerializer are also detected.
• It is allowed to deserialize such a conflicting key for both sealed and open polymorphic hierarchies. Previously, it was possible in the sealed hierarchies alone due to missing assertion. See #1664 for details.

General improvements

• Add .serialName to MissingFieldException for clearer diagnostics. (#3114)
• Generate unique Automatic-Module-Name entries for metadata JARs. (#3109)
• Revised ProGuard rules and added R8 tests. (#3041)
• CBOR: Improved error message when a byte string/array type mismatch is encountered. (#3052)

Bugfixes

... (truncated)

Sourced from org.jetbrains.kotlinx:kotlinx-serialization-core's changelog.

1.10.0 / 2026-01-21

This release is based on Kotlin 2.3.0 and contains all of the changes from 1.10.0-RC. The only additional change is a fix for ProtoBuf packing of Kotlin unsigned types (#3079). Big thanks to KosmX for contributing the fix.

For your convenience, the changelog for 1.10.0-RC is duplicated below:

Stabilization of APIs

kotlinx-serialization 1.10 and subsequent releases will be focused on stabilization of existing APIs. The following APIs and configuration options are no longer experimental because they're widely used without any known major issues:

• Json configuration options: decodeEnumsCaseInsensitive, allowTrailingComma, allowComments, and prettyPrintIndent. (#3100)
• @EncodeDefault annotation and its modes. (#3106)
• JsonUnquotedLiteral constructor function (#2900)
• JsonPrimitive constructor function overloads that accept unsigned types. (#3117)
• JSON DSL functions on JsonElement with Nothing? overloads. (#3117)

Readiness for return value checker

Kotlin 2.3.0 introduces a new feature aimed at helping you to catch bugs related to the accidentally ignored return value of the function. kotlinx-serialization 1.10.0-RC code is fully marked for this feature, meaning that you can get warnings for unused function calls like Json.encodeToString(...). To get the warnings, the feature has to be enabled in your project as described here.

Polymorphism improvements

Polymorphic serialization received a couple of improvements in this release:

New subclassesOfSealed utility to automatically register sealed subclasses serializers in polymorphic modules (#2201). Use it in your SerializersModule when configuring a polymorphic hierarchy which contains both abstract and sealed classes. For example, when root of your hierarchy is an interface, but most of your inheritors are sealed classes. The new function will register all known sealed subclasses for you, so you don’t need to list them one by one. This makes writing your SerializerModules much faster and simpler. Big thanks to Paul de Vrieze for contributing this feature.

Class discriminator conflict check rework (#3105). If a payload already contains a property with the same name as the configured discriminator (for example, type), it is called a class discriminator conflict. To produce a correct output and allow more inputs to be deserialized at the same time, the following changes were made:

• Conflicts introduced by JsonNamingStrategy transformations are now detected during serialization as well and will cause SerializationException. It also affects non-polymorphic classes.
• Conflicts from ClassDisciminatorMode.ALL_JSON_OBJECTS and SerializersModuleBuilder.polymorphicDefaultSerializer are also detected.
• It is allowed to deserialize such a conflicting key for both sealed and open polymorphic hierarchies. Previously, it was possible in the sealed hierarchies alone due to missing assertion. See #1664 for details.

General improvements

... (truncated)

• 370c4e3 Prepare 1.10.0 release (#3142)
• eaa4b0b Merge remote-tracking branch 'origin/master' into dev
• 0311f16 Fix ProtoBuf packing for kotlin unsigned types (#3079)
• a19df8c Add a disclaimer to "Other community-supported formats" section and slightly ...
• 2f8a874 Add JSON5 to community-supported formats (#3134)
• 975af2c Actualize releasing process document
• e8be81f Prepare 1.10.0-RC release
• e334d1c [CBOR] Fix various bugs in the decoder implementation
• d7ca108 Merge remote-tracking branch 'origin/master' into dev
• a5a3c97 IR inliner: Enable intra-module mode for kotlinx.serialization (#3128)
• Additional commits viewable in compare view

Sourced from org.jetbrains.kotlin.plugin.compose's releases.

Kotlin 2.3.0

Changelog

Analysis API

• KT-80082 K2. False positive "Cannot resolve method" for self-bounded generic with wildcard return type in Java interop
• KT-80303 Move :native:analysis-api-klib-reader to :libraries:tools

Analysis API. Code Compilation

• KT-70860 K2 IDE / Kotlin Debugger: CCE “java.lang.String cannot be cast to java.lang.Void” on evaluating not-null variable on the line with assigning null to that var
• KT-78554 K2 IDE / Kotlin Debugger: ISE “No override for FUN IR_EXTERNAL_DECLARATION_STUB” on calling toString() for local class instance during evaluation
• KT-73201 K2 IDE: Error while evaluating expressions with local classes

Analysis API. FIR

• KT-81378 Expected expression 'FirFunctionCallImpl' to be resolved caused by suspend {}
• KT-80473 Add events for tracking LL activities
• KT-46375 Analysis API: Support cross-file class redeclaration checks using indices
• KT-80471 Analysis API: Deduplicate equivalent call candidates in resolveToCallCandidates
• KT-79653 [Analysis API] ContextCollector: BODY context of enum classes doesn't contain enum entries
• KT-75858 K2 AA: False positive 'property must be initialized' on incremental analysis with 'field' usage and semicolon in setter
• KT-80231 AnnotationArgumentsStateKeepers doesn't restore the initial annotation in some cases
• KT-80233 Pull mutation out of AnnotationArgumentsStateKeepers
• KT-71466 LLFirBuiltinsSessionFactory uses createCompositeSymbolProvider
• KT-76432 JavaClassUseSiteMemberScope: Expected FirResolvedTypeRef with ConeKotlinType but was FirUserTypeRefImpl

Analysis API. Infrastructure

• KT-80717 Support IntelliJ Bazel build in the Kotlin Coop development mode

Analysis API. Light Classes

• KT-80656 Duplicate no-args constructor in PSI
• KT-60490 Symbol Light Classes: Property accessors from a delegated interface don't present in the delegating class
• KT-79689 SymbolLightClassForClassLike.toString() causes PSI tree loading
• KT-80690 Private interface functions are not present in light classes
• KT-80256 K2: Certain actions in JPA code causes infinite PIEAE: "Element class CompositeElement of type REFERENCE_EXPRESSION (class KtNameReferenceExpressionElementType)"
• KT-79012 Add a high-level overview of light classes

Analysis API. Providers and Caches

Fixes

• KT-81476 Analysis API: AlreadyDisposedException from low-memory cache cleanup
• KT-80911 Analysis API: Execute session invalidation in a non-cancelable section
• KT-81242 Analysis API: Add UUID/lifetime properties to LL FIR session structure logging
• KT-80622 Analysis API: Visualise LL FIR session structure & weight
• KT-80904 Analysis API: "Invalid dangling file module" exception during session invalidation
• KT-78882 K2 AA: Calling containingSymbol on getProgressionLastElement causes exception

... (truncated)

Sourced from org.jetbrains.kotlin.plugin.compose's changelog.